Computer network with diagnosis computer nodes

ABSTRACT

The invention relates to a computer network for configuration, installation, monitoring, error-diagnosis and/or analysis of several physical technical processes, in particular electrical drive processes, which occur under the control, regulation and/or monitoring of several process computer nodes, connected by means of at least one common communication system to at least one diagnosis computer node, in which one or several configuration, monitoring and diagnosis services and/or functions are implemented, provided for the processes and/or the process computer nodes and/or the data processing processes running therein, whereby the common communication system is achieved by means of the Ethernet, or a similar asynchronous and/or bus or communication system working with a stochastic access method.

CROSS-REFERENCES TO RELATED APPLICATIONS

This application is a submission to enter the national stage under 35U.S.C. 371 for international application number PCT/EP2003/050349 havinginternational filing date 29 Jul. 2003.

STATEMENT REGARDING FEDERALLY-SPONSORED RESEARCH AND DEVELOPMENT

Not Applicable

REFERENCE TO AN APPENDIX

Not Applicable

BACKGROUND OF THE INVENTION

1. Field of the Invention

The invention relates to a computer network for the configuration,installation, monitoring, error diagnosis and/or error analysis ofplural technical-physical processes. These may be in particularelectrical drive processes which run under control, regulation and/ormonitoring by plural process computer nodes (in the example of anelectric drive system: drive regulator). The process computer nodes areconnected to at least one diagnosis computer node via a sharedcommunication system. In the diagnosis computer node, one or moreconfiguration, monitoring and diagnosis services or functions is/areimplemented, which are allocated to the processes and/or the processcomputer nodes and/or to the data processing operations running therein.

The invention further relates to a diagnosis computer node for the saidnetwork. This is formed as a server with interfaces for at least onedatabase and for communication with at least the process computer nodesand with other client computer nodes. The invention further relates to acommunication computer node or a communication module, the latter beingformed as a software and/or firmware module, which is respectivelysuitable for use in the said network.

2. Description of the Related Art

From a conference volume to accompany the congress “SPS IPC Drives”,which took place in Nürnberg in November 2001, the technical article“Info-Portal für anlagenübergreifende Prozessvisualisierung und-management via Internet” (authors: Andreas Kitzler und Werner Felten)was disclosed. This proposed a communication structure in which plural,mutually independent automation systems, cells or appliances may becombined, monitored, visualised and the like via an information port. Atthe information port, access can be gained to the Internet. Thecommunication between the automation cells (known as Supervisory Controland Data Acquisition—SCADA) on the one hand and the central web serverof the information port on the other is effected via standard interfaceson the basis of the extensible mark-up language XML. To this end, eachautomation system is provided with what is known as an XML-agent forcommunication with the information port on the basis of TCP-IP. Thusmanagement should be able to evaluate in a qualified manner variousautomation cells or SCADA systems via the web. However, the individualsensor data have to be collected on the level specific to them, preparedthere and made available to the information port via the XML agentbefore they can be transported from the information port via the web.

From DE 196 14 748 (A1-published and unexamined specification, andC2-patent specification), an error diagnosis system is known in which adiagnosis computer node communicates via plural bus systems also on thebasis of the communication protocol TCP/IP (Transport ControlProtocol/Interface Program) with control station computer, controlprocess computer and field process computers. For communication betweenthe field process computers on the one hand and the diagnosis computernode on the other, a serial field bus according to the standard RS485 isused, wherein the diagnosis computer node dominates the serial field bus(RS485) according to the master/slave principle. The bandwidth for thedata transmission (RS485 interfaces) is not sufficient with theincreasing data inundation. The data to be presented on the userinterface cannot be transmitted quickly enough due to the ringcommunication structure within a field process computer cluster. Ittakes about 50-60 ms to scan one parameter—in appliances with about 500drives, for example, any error occurring would only be notified aftermore than a minute. Each parameter is transmitted individually, and thetransmission of software packages is not possible.

BRIEF SUMMARY OF THE INVENTION

The object of the present invention is to develop a hardware and inparticular software tool for the diagnosis of complex technicalappliances and systems which is tailored to the requirements and needsof the user and in particular meets the following requirements:

Versatile functions for monitoring and diagnosing large drive systems:

The object of the invention is to develop a hardware and in particularsoftware tool for monitoring and diagnosing in particular large drivesystems. The diagnosis system is intended to offer comprehensive,versatile functions which are tailored to the currently very differentneeds of the various user groups of the client.

(2) Easy-to-use, transparent user interfaces:

The user interface of the diagnosis system is the only part of thesoftware with which the client comes into contact. In this sense it isthe “bulletin board” of the software and is critical for acceptance andjudgment thereof by the client. In planning the user interface, thisshould be so contrived that it is easy to use even by not very highlytrained staff. The large number of data to be indicated in the diagnosisof large appliances must be graphically prepared and presented in anergonomic diagram to the user.

(3) Shortening of the time necessary to detect a possible error:

The usefulness of the diagnosis system to the client will be that he ispresented with data necessary for detecting and correcting the errorimmediately after an error has occurred. Thus the time can be reducedduring which the appliance is not productive.

(4) Situation-dependent presentation of diagnosis data

The diagnosis system should make available the right data at the righttime at the right place:

-   -   Preparation of the diagnosis information according to the        requirements of the respective user circle (e.g. appliance        operator, technician, installer)(→the right information)    -   Indication close to the time of diagnosis data directly after an        error has occurred (→at the right time)    -   Access to THE DIAGNOSIS SYSTEM by any PCs of the client without        installation cost—both in the local client network and via        remote access (→at the right place).

(5) Reduction of critical appliance states by prophylactic maintenanceand constant monitoring of the appliance:

In future, the diagnosis system is to contain mechanisms which help todetect possible oncoming failure of appliances and to inform the client.Thus the reliability of the drive system can be further increased.

(6) Comprehensive diagnosis/measuring operations via rapid Ethernetinterfaces, including the Ethernet overall concept of the machine inorder for example to measure, record and evaluate a reference signal ofa real leading axle.

(7) Prophylactic diagnosis (e.g. transmitter failure likely in . . .days).

(8) An “expert system” is intended to ensure error localisation within10 minutes maximum and simplify error correction substantially.

(9) Web browser functions.

(10) The diagnosis system must be able to run on plural platforms (e.g.diverse control stations).

(11) Integrated data protocolling/analysis (register values, commands)must be available without additional hardware (data analyser).

(12) Cyclical data protocolling at a central database server.

(13) Access option for the machine manufacturer to drive systemssupplied via remote diagnosis.

(14) Operator guidance and parameter handling (configuration,installation, error search, software updates) are to be substantiallyimproved.

(15) Development of branch-overlapping solutions

In spite of taking clients' wishes into account, the diagnosis systemfor branch-overlapping use is to be developed so that use in otherbranches (e.g. machine tools, textile machines) is possible withoutgreat complication/expense.

(16) Preparation of software tools for the installation of drive systemswith in future up to 500 axles

Drive systems with more than 300 axles can only be installed withoutsoftware support with excessively high cost. To this end, with thediagnosis system according to the invention a suitable software tool isto be developed.

(17) Shortening of the installation time and reduction of theinstallation costs:

By means of the diagnosis system, the costs of installation are to bereduced in the long term by the delivery of suitable software-supportedmethods.

(18) Worldwide access to the technical-physical processes of theappliance, in particular drive systems, for rapid, economical diagnosis:

For rapid and reliable service and for appliance diagnosis, worldwideaccess to the drive system will be possible.

On the other hand, in order to prevent the disadvantages from the priorart from arising in the computer network having the features mentionedin the introduction, it is proposed according to the invention that theshared communication system between the process computer node and thediagnosis computer node is realised with the Ethernet or another bus orcommunication system operating asynchronously and/or with a stochasticaccess method. An access method of this type is known for example underthe abbreviation “CSMA/CD” (Carrier Sense Multiple Access/with CollisionDetection). This industrial Ethernet use for realising a communicationinfrastructure permits a higher bandwidth for data transmission comparedto the prior communication via RS485 and the associated USS protocol, sothat larger quantities of data can be transmitted from the processcomputer node to the diagnosis computer node. There is an increasingneed for this, due to the increasing complexity of the technicalappliances with an increasing number of process computer nodes andassociated technical-physical processes. Furthermore, the Ethernet hasproved a substantial standard in offices for transmitting largequantities of data. By the use according to the invention of theEthernet with the protocol TCP/IP also known per se, the path is clearedfor the diagnosis system according to the invention to be compatiblewith and/or combined with the Internet. Thus the advantage is gainedthat diagnosis data can be sent via the Internet. In addition, atechnical appliance can be monitored with a large number of processesfrom any client node, in particular via the Internet.

In order to be able to process the extensive quantities of data arisingin a practical manner, a decentralised diagnosis together withpre-processing is advantageous. It is also practical to move extensivediagnosis functions as close as possible to the technical-physicalprocess or apparatus concerned. In this respect, according to anadvantageous embodiment of the invention, a communication unit orcomputer node is interposed between the Ethernet or the other bus orcommunication system and at least one of the process computer nodes,thus connecting the respective process computer node to the Internet orother bus or communication system. The communication computer node orcommunication unit can additionally also undertake event- and/orenquiry-based communication to the diagnosis computer node.

In particular, when in a further configuration of the invention thecommunication unit or the communication computer node is so formed thatit communicates via XML protocol and/or as an XML-based interface(XML—Extensible Markup Language) with the diagnosis computer node, inprojecting and configuring the technical appliance to be monitoredthereby, it is possible to react very flexibly and with relatively lowcost to technical requirements and client wishes. On the basis of theinvention, a standardised, versatile network-computer structure can becreated, which can be easily extended by further functions.Particularly, with the use of XML protocol and/or XML-based interfaces,the diagnosis data can be so prepared from the process computer nodeand/or communication node for the diagnosis computer node that thesedata can be transmitted easily via the Internet from the diagnosiscomputer node to client computer nodes.

In order to be able to manage the extensive quantities of data in apractical manner via decentralised pre-processing, according to oneembodiment of the invention it is provided that the communication unitor communication computer node is provided with functionalities forerror search or diagnosis in the region of at least one of the processcomputer nodes or of a technical-physical process. With this notion,extensive diagnosis functions can be located close to the componentsconcerned.

The Internet-compatibility of the diagnosis system according to theinvention is enhanced if according to an embodiment of the invention thediagnosis computer node is formed to make available or at least supportweb-based user interfaces for client computer nodes. This can beeffected via data remote transmission and/or a long-distance trafficnetwork (e.g. Internet). It is further within the scope of the inventionif in addition the diagnosis computer node is provided with functioncomponents which support the education of the user interfaces in theclient computer node.

It is problematic whether the user at a client computer node mustconfident that the client user interface is reproducing (diagnosis) dataand information which are still substantially up-to-date or close intime. Any failure of the diagnosis server should be detectable, andfurthermore errors and other events in the technical-physical processand/or process computer node are to be capable of being communicated tothe user close to time via the user interface of the client computernode allocated to him.

To solve this set of problems, within the scope of the general inventivenotion, a diagnosis computer node having the following features isproposed for use as a server in the network outlined above:

-   -   The diagnosis computer node is set up to operate as a server and        has interfaces to at least one database, for communication with        the communication and/or process computer node and for        communication with other client computer nodes;    -   The one or more interfaces to the other client computer nodes        are realised by using a Servlet container (known per se), which        transmits diagnosis data to the client nodes;    -   These diagnosis data are obtainable from the interfaces for        communicating with the communications and/or process computer        node;    -   The one or more above-mentioned interfaces which are allocated        to the communication and/or process computer nodes are realised        on the basis of the Ethernet;    -   A diagnosis channel is formed, which comprises one or more        Ethernet interfaces, which are allocated to the communication        and/or process computer nodes;    -   The diagnosis channel further comprises an event management        unit, which can access the database and can process diagnosis        data obtained at the Ethernet interfaces;    -   Further, the diagnosis channel comprises an event monitoring        unit, which is formed on the basis of the Servlet container and        makes available output data from the event management unit to        one or more Applets on external client computer nodes.

It is thus possible to transmit data, in particular diagnosis data incycles between the diagnosis computer node and the user interface of aclient computer node. Thus a user at the client computer node can beinformed close to time of events arising in the region of the processcomputer node and/or of the technical-physical processes. Thus a widevariety of appliance information can be made available on the userinterface of the client computer node in a comfortable manner. The datatransmission can be carried out particularly advantageously with Javatechnologies, in particular a Java Servlet on the diagnosis computernode as a server and a Java-Applet in the client computer node. Thus itis also possible to make available diagnosis information in the form ofwebsites to a user on the client computer node. In this case, the use ofJava-Applets offers very versatile representation options, which areeasily extensible by bought-in Applets with graphical capabilities.

The solution to the above set of problems is assisted by the diagnosischannel according to the invention in the diagnosis server, by means ofwhich a cyclic communication can be effected, wherein data packages areregularly exchanged. If a data package is missing, it can be detected inthe client computer node that an error has occurred (“event+heartbeat”).The heartbeat corresponds as it were to the dead-man's button known inparticular in the field of railway safety technology. By means of thediagnosis channel, therefore, a display of diagnosis data originatingfrom the process computer node can as it were be triggered via diagnosisserver or diagnosis computer node to the client computer node on hisuser interface. The representation of the error on the user interface isno longer dependent on an enquiry being sent to the diagnosis server bythe client computer node due to the diagnosis channel according to theinvention. Rather, the process computer nodes, optionally viaindividually allocated communication nodes, can itself indicate as itwere new events, in particular errors. This mechanism is substantiallysupported by the diagnosis channel in the diagnosis computer node inthat diagnosis or error data notified via the event monitoring unit bythe process computer node are forwarded to the user interface of theclient computer node for a user at that interface.

According to a particular configuration, the interfaces in the diagnosiscomputer node are contrived for communication with the communicationand/or process computer nodes by means of XML protocols. Thusproprietary solutions which have restricted applicability are avoided.

In the diagnosis computer node, all diagnosis data are intended to bemade available to the user interfaces on the client computer nodes in aweb-based manner. It has turned out to be particularly advantageous forthis purpose to have a combination of the web-server Appache with theServlet-engine “Tomcat”.

In the diagnosis computer node according to the invention and indicatedabove, the diagnosis channel ensures in the case of an event, inparticular error, to prompt a reaction from the client computer nodethereto with his user interface. If an error or event occurs,corresponding diagnosis data are picked up at the Ethernet interface ofthe diagnosis channel, and are allocated to the communication units,communication and/or process computer nodes. The event management unitcan access the diagnosis or event data in the form of a telegram forexample at the Ethernet interface. The event or diagnosis data areprocessed and a corresponding datum is written into the database. Theoutput data from the event management unit pass to the event monitoringunit applied in the Servlet container. In the example of the Intranet,this event monitoring unit transmits at its output a datumadvantageously direct to the client computer node, without theinterposition of a web server. The datum contains a prompt to demandrepresentative diagnosis data from the diagnosis server due to events orerrors. Thus the need for constant polling throughout the period ofoperation, which would require increased data transmission capacities,is avoided.

To connect the process computer node to the Ethernet or anotherasynchronously operating communication system with the diagnosiscomputer node, and in particular to create the option of an event-basedcommunication between process computer nodes and diagnosis computernodes, extensive diagnosis functions being located as close as possibleto the technical-physical process, in the scope of the general inventivenotion, a communication computer node or a communication unit areproposed as a software and/or firmware module, which is suitable for usein the computer network outlined above and is distinguished by thefollowing features:

-   -   The communication computer node or the communication unit has a        first interface which is allocated to the at least one diagnosis        computer node;    -   This interface is programmed or formed for communication via        protocols of the TCP/IP family, including UDP/IP, preferably on        the basis of the Ethernet;    -   The communication computer node or the communication unit has        one or more second interfaces which is/are allocated to one or        more process computer nodes;    -   The first and one or more second interfaces may be coupled        together via one or more information brokers;    -   The one or more information brokers are respectively set up in        terms of program and/or circuit technology as sub-units for        bidirectional, enquiry- and/or event-based data communication,        which takes place between the first and the one or more second        interfaces.

The purpose of the communication unit or communication computer node isto roll out all communication tasks between the process computer nodeand its outside world. This includes for example access to parameters ofthe process computer node, e.g. of the drive regulator, the down- andup-load of regulator firmware for example and associated data records,as well as the delivery of diagnosis functionalities.

With respect to the realisation of hardware of the communication nodeaccording to the invention, it might be advantageous to manufacture afree-standing structural unit with the communication functionsincorporated therein and to mount this on the printed circuit board forthe process computer node. Alternatively, the communication nodehardware may be incorporated wholly or in part in the circuit on theprinted circuit board of the process computer node and/or on that of thediagnosis computer node. Alternatively, it is within the scope of theinvention to realise the communication node as a “PC” as it were withits own housing, which can be snap-fitted on to a rail-type mount forthe process computer node.

As an operating system for the communication node according to theinvention (communication unit or communication computer node), the useof Linux has been found advantageous. In addition, C++ is suitable as asufficiently versatile and powerful programming language.

With the concept according to the invention of the communication nodebetween the process computer and diagnosis computer, there is the optionfor transmitting data to the outside world via XML-based protocols(instead of proprietary protocols). With the mark-up language XML, whichis widespread and known per se, for Internet applications in combinationwith the delivery of platform-independent XML parsers, there is thefurther option of simply exchanging data in heterogeneous systemenvironments. By way of validation mechanisms (XML models) that arealready available, the structure and admissible content of a telegramcan be established simply, and testing for quality takes placeautomatically. As a character-based protocol, an XML-based telegram iseasy to generate and if necessary to process by hand or by simplescripts.

In order to be able to implement the most extensive diagnosis functionsas close as possible to the technical-physical process, according to anadvantageous embodiment of the invention it is proposed that the one ormore information brokers comprise function components which are formedto perform an error search or diagnosis in the region of the processcomputer node and/or technical-physical processes. In particular in thisconnection, a further advantageous embodiment of the invention involvesthe installation of interpreters for the loadability of scripts knownper se on the communication computer node or unit, which interpretersare formed for access to function elements or functionalities in theinformation broker(s) for the purpose of carrying out monitoring anddiagnosis functions. One advantage achievable thereby consists in themore effective error search: by means of the scripts in combination withthe language PERL, in a relatively simple manner, efficient error searchconditions can be installed or loaded by the diagnosis computer node onthe communication node. Thus the functionality available on thecommunication node can be extended once again.

It is within the scope of the invention that the communication unit orthe communication computer node in certain cases operates as a serverwith respect to the diagnosis computer node (as client) if on the partof the diagnosis computer node requirements are present at informationservices, which are to be realised for example by information brokers inthe communication node.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS

Further details, features, advantages and effects on the basis of theinvention will appear from the following description of preferredembodiments of the invention and from the drawings given by way ofexample. The drawings show:

FIG. 1 a schematic appliance diagram of the diagnosis system accordingto the invention with local and worldwide access to diagnosis data;

FIG. 2 a schematic block diagram of an example of a communication systemof an electric drive system provided with the diagnosis system accordingto the invention;

FIG. 3 shown in schematic block representation, the basic structure ofthe diagnosis system according to the invention;

FIG. 4 a detailed block diagram of the internal structure of thediagnosis computer node;

FIG. 5 a similar block diagram of the internal structure of thecommunication computer node;

FIG. 6 a user interface, by way of example, on a client computer nodefor an appliance-based appliance image with the example of a printingpress, generated by means of a Java-Applet in combination with acorresponding Servlet on the diagnosis computer node;

FIG. 7 a further, similarly generated user interface via adrive-system-based appliance image with the example of a printing press.

In describing the preferred embodiment of the invention which isillustrated in the drawings, specific terminology will be resorted tofor the sake of clarity. However, it is not intended that the inventionbe limited to the specific term so selected and it is to be understoodthat each specific term includes all technical equivalents which operatein a similar manner to accomplish a similar purpose. For example, theword connected or term similar thereto are often used. They are notlimited to direct connection, but include connection through othercircuit elements where such connection is recognized as being equivalentby those skilled in the art. In addition, many circuits are illustratedwhich are of a type which perform well known operations on electronicsignals. Those skilled in the art will recognize that there are many,and in the future may be additional, alternative circuits which arerecognized as equivalent because they provide the same operations on thesignals.

DETAILED DESCRIPTION OF THE INVENTION

According to FIG. 1, an electric drive system for a large number ofaxles 1 to be driven synchronously with one another, e.g. of a printingpress provided with a large number of electric motors 2, each drivingone axle 1. The electric motors 2 are each triggered or regulated viarespective converters 3 with upstream process computer nodes 4, realisedin the present printing press drive system as drive regulators. Tocommunicate with a diagnosis computer node, respective communicationcomputer nodes 5 are connected upstream of the process computer nodes.The converter 3, the process computer node 4 and the communicationcomputer node 5 can be incorporated structurally into a common assembly,as is shown in the drawing, which is housed in a respective switchcabinet 6.

According to FIG. 1, the diagnosis computer node can also communicatewith a control station, plural client computer nodes for diagnosis andvia an Internet router or ISDN or in an analogue manner via the Internetwith one or more geographically remote client computer nodes for remotediagnosis. Thus the diagnosis data prepared at the respective driveprocess of the electric motors 2 by means of the process computer node 4and/or of the communications computer node 5 may be retrieved via thediagnosis computer node both locally and from any other location.

According to FIG. 2, the individual process computer nodes 4 areconnected together in the context of a ring structure for synchronisedcommunication, in which case one of the process computer nodes 4 (theone printed darker in each case in FIG. 2) always operates as thecommunication master. This simultaneously has an interface forasynchronous communication via the Ethernet with plural control computernodes SPS. In order also to support cross-communication betweenindividual rings with process computer nodes 4, a multi-link controllerMLC is also introduced as a structural element (known per se from U.S.2003/0100961 A1).

In the reference plane, (diagnosis) data are constantly being requiredfrom the plane of the process computer node 4. These are essentiallysystem data such as status and error messages, maintenance data andrecords for quality control. In order to evaluate the data, a diagnosiscomputer node is available in the reference plane as is shown in FIG. 2.In this case also, the Ethernet known per se is also made available as acommunication medium both with the individual process computer nodes 4and also with the diagnosis stations in the reference plane, which mayform client computer nodes with the user interfaces. The OSI layer modelknown per se permits complex communication mechanisms between theprocess computer plane and reference plane. Since the diagnosis is to beeffected independently of the remaining communication, each processcomputer node 4 is reachable via the Ethernet by the diagnosis computernode (and vice versa). Thus, inter alia, the advantage is gained thatcommunication problems in the synchronised ring bus of the processcomputer node can be mutually detected.

Definition of important terms:

Event An event is a datum which is sent by a drive regulator (processcomputer node at the technical-physical process) upon occurring at thediagnosis server (diagnosis computer node). It appears in the eventdisplay of the user interface and in the logbook. Events are for exampleerror messages, messages about the start/stop of records, maintenancemessages etc. Every event has an unambiguous event identification viawhich an event description can be retrieved in the documentation.

Record With a record, any parameter curves can be picked up by anyregulator and stored in a database.

Monitoring view The monitoring view is a graphic representation of oneor more parameters of one or more regulators. It serves to monitor thevalues curve of these parameters for deviations from the norm (e.g.monitoring of the motor temperature).

Parameter list The parameter list contains all parameters available toone type of regulator.

Long-term record A record whose data are stored on the diagnosis serverin a database. Opposite to ring memory record.

Ring memory

record A record whose data are stored in a ring memory of the processcomputer node. Only upon completion of the record can the data be storedon the diagnosis server.

Configuration

Wizard A sequence of individual pages on which the user can makesettings. Each step in the configuration comprises a number of functionsand is shown on one page. According to what the user does in theprevious step, a corresponding consecutive page is displayed (e.g. inthe configuration of the record: option in step 1: ring memory orlong-term record: according to the selection, the user receives pagesdisplayed for configuring the ring memory or the long-term record).

FIG. 3 gives an overview of the basic structure of the diagnosis system.The user has various web-based user interfaces available, which presenthim with the functionality of the diagnosis system in a manner suited tohim. For operation of the system, it is unimportant whether the user islocal to the appliance or at another location.

The functions desired by the user are forwarded by the user interfacesto the diagnosis computer node. Here, every functionality which isavailable in the interface is implemented. Further, the diagnosiscomputer node undertakes to store all the data occurring in the databaseDB. All data specific to the appliance such as for example the applianceconfiguration or component databases, all data specific to diagnosissuch as e.g. long-term records or ring memory records and all datarelating to application, are managed in the database.

If relevant data are made available for diagnosis by the control orcontrol station e.g. of a printing press, these can be further processedby special components incorporated in the diagnosis computer node.

The tasks incoming from the user interface at the diagnosis computernode are processed there and converted into commands that will beunderstood by the corresponding regulator. The communication betweendiagnosis computer nodes and communication computer nodes with aconnected regulator is effected via Ethernet and XML protocols supportedthereon. At the communication computer node, the tasks received from theapplication server are carried out and the result is sent back to thediagnosis computer node.

Each of the supported process computer nodes, e.g. regulators, mustoffer an XML-based interface in order to permit the diagnosis computernode access to the required data. This can be effected e.g. by means ofa communication computer node (“communication PC”), which is eitherincorporated in the process computer node (e.g. b maXX 4600) or is addedto the process computer node as a plug-in card. Alternatively, theXML-based interface of the process computer node can also run withoutcommunication PC hardware as part of the diagnosis computer node. Thecommunication between the interface units on the diagnosis computer nodeand the process computer node hardware is then carried out viaproprietary protocols and RS232 or Ethernet.

The requirements mentioned in the introduction require acomponent-based, distributed architecture of the diagnosis system.According to the general principles of software development, datacapture, data processing and data storage and the user interfaces are inmodular form and are separate from one another. Thus a transparent andmore calibratable structure is achieved, which can be easily extended byfurther functionalities. It can thus be ensured that the diagnosissystem grows along with the increasing number of drives(calibratability). By the use of Ethernet and TCP/IP for thecommunication between the communication PCs, the diagnosis computer nodeand the applications, there is a substantially larger bandwidthavailable for data transmission. This results in a substantially fasterdiagnosis system than that of DE 196 14 748 mentioned in theintroduction.

Further, the component-based structure simplifies coverage of the largefunction scope of the diagnosis system. For every user group, an userinterface tailored to their individual needs can be developed, which hasaccess to the underlying infrastructure (diagnosis computer node).

By separating user interface and implementation of the functionality inthe diagnosis computer node, new applications can be developed in futurewith less expense. By using modem software technologies, the Internetcan be used as a communication medium that is available and acceptedworldwide. Thus it is not important whether monitoring of the applianceis carried out locally on site or from another site, e.g. the servicedepartment. By using current Internet browsers for the user interfaces,the installation costs for the user are substantially reduced and thenumber of hurdles for the user in using the diagnosis system issignificantly reduced.

The component-based architecture furthermore permits the support ofnewly developed methods of monitoring and diagnosing drives in that newfunctions are incorporated as components in the diagnosis computer node.

Substantial advantages of the diagnosis system according to theinvention consist in particular in the following:

The client has universal access by the web interface to the diagnosisfunctions:

-   -   The right information close to time at the right place    -   Simple user interface by way of web browsers    -   User guidance simplifies operation and configuration    -   The web interface is platform-independent    -   Operation possible via the Internet if desired.

(2) The client receives data concerning the state of the appliance whichhave been prepared for him:

-   -   Data preparation in the form of graphic representations    -   Prophylactic diagnosis.

(3) The substantially extended diagnosis options permit:

-   -   Extended monitoring of the appliance    -   Simpler localisation of the cause in the case of an error.

(4) The functions for installation support permit:

-   -   Faster installation→reduction in costs    -   Improved quality of installation by specified and documented        acceptance protocols.

A function group “software update” permits the installation or updatingof a firmware of the process computer node e.g. to firmware. All actionscarried out in this function group are detected in a log file. It is aprecondition for installation or updating of the firmware that theregulators selected have unambiguous regulator identification. Thefollowing actions must be possible:

Selecting drives

The user selects the drives to be updated from a drive list.

2. Selecting firmware

The user selects the firmware which is to be loaded on to the drives tobe updated.

3. Carrying out the software update

After the display of a warning notice, the software update is carriedout.

A function group “configure events” offers the option of recording anyevents in the events display and in the logbook. The event brokerpresent in the communication PC of the respective process computer nodeis configured by means of the functions mentioned below, so that itmonitors the desired parameter combinations for occurrence of theconfigured event. If the event does occur, it is sent to the diagnosiscomputer node and is displayed there in the event display. The followingactions may be possible for example:

Selecting drives

The user selects the drive for which an event is to be configured ordeleted.

2. Configuring event

The user configures an event by means of a configuration wizard

3. Deleting event

The user deletes an event from a list with current events. Events whichare present as standard, e.g. errors, cannot be deleted.

4. Sending event configuration to drive

The user sends the configured event to a drive selection and activatesthe same.

A function group “scripts” offers the option of carrying out complexdiagnosis functions. In order to make complex enquiries of parameters,PERL scripts can be written which are sent to the correspondingcommunication PC and are executed there. The following actions are to bepossible:

Loading of the script on to the server

The user loads the script from the communication PC of a drive on to theserver.

2. Loading of the script to the drive

The user loads a script selected from a list on to a selected drive.

3. Editing script

The user edits a script.

4. Execution of the script on the communication PC

The user starts the script on a drive.

Below, an overview of the architecture of the diagnosis computer node ofthe diagnosis system is given. FIG. 1 shows a detailed structure of thediagnosis system. It consists substantially of three planes:

Client computer node with user interfaces

All functionalities of the diagnosis system can be operated via the userinterfaces. For the user of the diagnosis system it should make nodifference whether he is at the appliance in the local network or isconnected to the application server via the Internet or a telephonedial-up connection.

Diagnosis computer node

This is the core of the whole application. Its functionality is dividedinto various components (managers). Each manager is self-contained andmakes available its functionality to the web-based user interface or toother server components. All data necessary for the function of themanager are stored in the connected database. In order to ensureencapsulation and consistency of these data, access is only permitted tothese databases via the functions made available by the manager. Thisalso ensures that a change in the database structure of one manager doesnot automatically lead to changes at other managers.

In order to make available the functionalities of the managers to theuser interfaces, a suitable infrastructure must be created (TomcatServlet container). For communication with the web interface forinstallation, monitoring and diagnosis, an Apache web server is to beused. This makes available HTML pages in which Java Applets areembedded. The data to be displayed on the interface is transmitted bymeans of SOAP (Simple Object Application-Protocol) to the appropriateunits. The user interface retrieves e.g. a function of the appliancemanager. The parameters to be transferred and the reference of thefunction are sent to the Intra- or Internet by means of the SOAPprotocol. In order to ensure the transparency of current firewalls, thefunction retrieval is sent in the form of an HTTP telegram. A web serveron the site of the application server receives the HTTP telegrams withthe SOAP content and forwards them to the SOAP handler. The SOAP handlerin the Tomcat Servlet container decodes the enquiry and retrieves thedesired function from the appliance manager. The function is executedand the return values are in turn converted into the SOAP protocol andsent to the interface as an HTTP telegram.

An essential property of a diagnosis and monitoring system is that theuser is informed close to time of events occurring at the appliance.This presents a problem for the architecture described above, since bothfor communication via SOAP and for the HTML pages, there is noevent-based reporting. As a remedy, events occurring at the appliance,e.g. the occurrence of an error or the update of a parameter value inone interface, must be communicated via an event channel to the userinterfaces or constantly polled.

Process computer node

The process computer node plane makes available to the diagnosiscomputer node the data from the process computer node. The processcomputer node must be connected. As already indicated, the diagnosiscomputer node consists of various encapsulated server components(managers) which make their functionalities available via the TomcatServlet container to the user interface or client computer node. Thecomponent-based structure is intended to ensure that the function scopeof the diagnosis system can be extended. The managers are realised asJava components. The individual managers are described below.

The appliance manager contains all the necessary data about theconfiguration of the appliance. This contains data concerning thecomponents present in the appliance, the grouping of components,addresses, etc. Functionalities are to be made available which permitthe appliance configuration to be represented in the form of variousoverview images. Furthermore, all documentations are to be madeavailable to the data contained in the appliance.

In planning the appliance manager, it should be ensured that by means ofthe functionalities of this component any appliances can be described inthe field of drive technology.

The event manager administers all events occurring in the diagnosissystem such as e.g. error messages or maintenance events. It gathers allevents that have occurred in the form of logbooks and makes themavailable to the user in a configurable representation. Further, theevent manager has functions by means of which any event monitoring canbe defined which is then configured by the event manager on thecorresponding regulators.

The record manager makes available functions by means of which anyparameters from any regulators can be recorded. It offers various typesof record which can be configured by the user. All data occurring in arecord are stored by the record manager in a database and if requiredmade available to other units, e.g. a graphics unit of the interface.

All functionalities in the diagnosis system are protected againstunauthorised access. Every user has a user identity and belongs to auser group which allows him a rights profile for access to thefunctionalities of the manager. These data are configured and stored inthe user manager. Every function in the managers has an unambiguousidentification. If a user wants access to a function, first the usermanager is asked whether the user has the appropriate rights to carryout this function. The database in which the user data are stored is tobe password-protected against unauthorised access.

The logging manager gathers all logging data from the connectedregulators and stores their log and debug messages in a database or inrolling log files.

The communication computer node or communication PC according to FIG. 5carries out communication tasks between the process computer node andthe outside world. The software structure for communication with theprocess computer node is described below.

Each appliance that is to communicate with the process computer nodemust respond thereto via a suitable software interface on thecommunication PC. By means of the communication PC, almost any softwareinterface based on the Ethernet or a serial interface can be realised.The software architecture on the communication PC is described below.Classification into the overall concept can be deduced from the commentsabove. FIG. 5 shows the software structure on the communication PC orthe process computer node.

Any functionality which is to be made available by the process computernode is realised in a software module (information broker or manager).For example, the information broker makes “parameters” available to aparameter interface via which any parameter of the process computer nodecan be read and written. The information broker “errors and events”presents any events and errors to the outside. The two informationbrokers “parameter demand data” and “cyclical setpoint values” carry outcommunication with the control. They are only available on theregulators which form the master in the sercos ring and thus mustcommunicate with the control. The information broker “software download”delivers functions for automatic up- and download of the regulatorfirmware. A parameter manager (not shown) acts as internal management ofthe regulator parameters on the flashcard. It is not relevant to thecommunication with the outside world.

The communication of the information brokers “parameters”, “error andevent” and “software download” with the outside world is effected viaXML-based protocols. All enquiries or responses are transmitted in XMLmessages defined by means of an XML model.

Each of the available brokers can process more than one enquiry at atime from one or more clients. Essentially, the communication PC of theprocess computer node communicates with the control and the diagnosiscomputer node. In communication with an SPS control, it must be ensuredthat the messages are processed in each case without an unnecessary timelag at a process of the process computer node, as these are ofsubstantial significance for operation of the appliance. Since theenquiries can only be processed sequentially on the processor of theprocess computer node, it must be possible to process enquiries from theSPS control in strict precedence. This should be ensured by allocatingpriorities for the enquiries. Each enquiry to one of the brokers on thecommunication PC is provided with a priority. According to this prioritythe enquiry is preferred or treated as subordinate.

In addition to the information brokers, there are further, in partoptional, software modules on the communication PC:

-   -   A logging server receives log and debug messages from the        information brokers and makes them available to the outside        world.    -   A web server offers a simple web interface for operation and        configuration.    -   An FTP server gives simple up- and download of firmware on to        the process computer node.    -   A client for time synchronisation supplies a matching time to        all communication PCs of an appliance.    -   By means of a PERL interpreter, any scripts can be carried out        with diagnosis or control functionalities.    -   The configuration manager carries out starting of important        services (e.g. automatic configuration of event monitoring for        an error in the technical- physical process) and management of        the configuration data of the individual software modules.    -   A Telnet access is available for maintenance purposes.

The software modules of the communication PCs are described below.

The object of the information broker “parameters” is to prepareXML-based parameter interface for access to the parameters of theprocess computer node. As protocol, an XML-based protocol defined bymeans of an XML model is used, which communicates via TCP/IP with theclient. From the viewpoint of the client, the following functions shouldbe available:

Reading of parameters

The information broker “parameters” should be able to read a group ofany parameters from the processor of the process computer node. In thiscase, in addition to once-only reading, the cyclical reading ofparameters should be possible. The client is to be able to set theinterval between reading operations and the number of readingoperations.

Writing of parameters

The information broker “parameters” should be able to write a group ofany parameters on to the process computer node.

The task of the information broker “errors and events” is to prepare anXML/based interface, via which a client is informed of events occurringat the regulator, without constantly having to enquire of the regulator.As a protocol, an XML-based protocol defined by means of an XML model isused, which communicates with the client via TCP/IP. From the viewpointof the client, the following functions are to be available:

Configuration of event monitoring

At the information broker “event”, it will be possible to specify anyentry conditions for an event, upon the occurrence of which a message issent to the client. If the event has occurred, in addition to theparameters taking part in the entry condition, it will be possible toscan further parameters from the regulator.

An accepted task will be confirmed by the broker.

The information broker “event” will have extensive functionalities whichoffer the client wide-reaching possibilities of forming entryconditions. An entry condition will be composed of plural parts, whichcan be linked together logically by AND or OR. Within each partialcondition, the value of the parameter currently scanned can be comparedeither to a comparative value sent within the configuration message orto the most recently read parameter value. Optionally, a tolerance limitcan be taken into account, which is settled with the comparative value.For the comparison, both all logical operators (<,>,<=, >=, |=) and thecomparison to a bit mask are to be carried out. In addition, for eachpartial condition, a trigger mode is to be taken into account whichindicates whether the event is to be sent the first time the eventcondition is encountered, upon disappearance of a condition alreadyencountered, or in both cases.

Notification of an event

When the configured event condition is encountered, an XML message is tobe sent to the client.

Ending of event monitoring

By means of an XML message provided for this purpose, event monitoringin progress can be ended.

Enquiry of the status of event monitoring

By means of an XML message provided for this purpose, the client canenquire of the information broker “event” whether event monitoring is inprogress or has already finished.

A difference from the information broker “parameters” is that there isno permanent socket connection to the client. After the configuration ofthe event, this is dismantled and only if the configured event arises isit re-assembled. To this end, on the part of the client a correspondingserver port must be available.

The information broker “cyclical setpoint values” effects part of thecommunication with the control. It is used in particular with printingpress applications provided there is a process computer node orregulator which is a sercos master in a drive ring.

The task of the information broker “cyclical setpoint values” is tosupply the regulator at regular time intervals with new setpoint valuesfrom the control. In this case, it receives telegrams sent from thecontrol and forwards them to the regulator. It should have the followingcapabilities:

Receiving of setpoint value telegrams from one or more controls

The information broker “cyclical setpoint values” will be capable ofreceiving setpoint value telegrams from one or more controls. Thecommunication with the control may run via a proprietary protocol and/orthe protocol UDP/IP.

Forwarding of setpoint values to the regulator

All setpoint value telegrams received by a control SPS will be forwardedwith the highest priority to the process computer control or regulator.

Monitoring of the setpoint value telegrams

For diagnosis purposes, it will be possible to forward the incomingtelegrams from the control both to the regulator and additionally to thediagnosis system.

The information broker “parameter demand data” effects some of thecommunication with the control. It is used particularly in printingpress applications provided it is a process computer node or regulatorwhich is the sercos master in a drive ring.

The task of the information broker “parameter demand data” is to makeavailable any parameter values to one or more controls close to time. Itwill have the following capabilities:

A control client sends any parameters in a requirement telegram to theinformation broker. This requests the parameter values with a highpriority from the regulator and sends back a reply telegram to thecontrol client. For communication with the control client, a proprietaryprotocol and/or TCP/IP may be used.

Monitoring of the requirement telegrams

For diagnosis purposes, it will be possible to forward the incomingtelegrams from the control both to the process computer node orregulator and additionally to the diagnosis system.

The task of the information broker “software download” is to transmitthe regulator firmware and complete data records between the diagnosiscomputer node and the regulator. The transmission of data is effected bymeans of the FTP protocol. It will have the following capabilities:

Download of a regulator firmware to the regulator as process computernode

The download of regulator firmware is effected in two stages: first bymeans of an FTP client the firmware is transferred in a list on theflashcard of the communication PC. In the second stage, the informationbroker “software download” is instructed by means of an XML telegram tochange the boot settings of the regulator in such a manner that the nexttime the regulator is booted up the new firmware is started.

Upload of a regulator firmware as process computer node

The upload of a regulator firmware is effected direct via the FTPprotocol. In this case, no support on the part of the information broker“software download” is necessary.

Download of a complete data record

As in the download of a regulator firmware, the download of a parameterdata record likewise takes place in two stages:

First, by means of an FTP client, the data record in a list on theflashcard of the communication PC is transferred. In the second stage,the information broker “software download” is instructed by means of anXML telegram to change the settings of the regulator in such a mannerthat the next time the regulator is booted up the new data record istaken into account.

Upload of a complete data record

The upload of a data record is effected direct via the FTP protocol. Inthis case, no support on the part of the information broker “softwaredownload” is necessary.

The task of the connection manager is to administer the interface to theregulator or process computer node. In this it will be possible tomanage various physical interfaces (e.g. serial, Ethernet or SPI). Eachenquiry to the connection manager is provided with one or 5 prioritylevels. Enquiries with the highest priority are sent by the connectionmanager to the (digital signal) processor process computer node beforeall other enquiries awaiting a response. Enquiries with a low priorityare always dealt with after all other tasks awaiting. Thus it can beensured that a task with the highest priority, e.g. from the control, isalways processed as the next enquiry on the process computer node.

In the process computer node, as a memory means a flashcard is allocatedto the communication PC due to the improved support by the Intel PXA255. However, for the process computer node or regulator, there has tobe an option of reading parameters from the flashcard and to write themon to the flashcard. This is ensured by means of the parameter manager.

Further services on the communication PC

Logging servers

All notices generated in the information broker processes are formattedand written to the console, into a log file or a message queue of thelog server. This log server can then send the messages to anyservers/computers.

In order to permit subsequent evaluation of the log files, variousmessage types are specified which simplify the interpretation of themessages (e.g. debug, data, error . . . ).

Script support

By means of script support on the communication PC, a versatile andfreely programmable interface is to be created, with which futurerequirements of monitoring and diagnosis are to be covered. By means ofa PERL interpreter, any scripts can run on the communication PC, whichhave access to the functionalities of the information brokers“parameters” and “errors and events”. Thus relatively complex monitoringfunctions can be carried out locally on the communication PC withoutloading the network by transmitting data. The scripts are transmitted bymeans of the FTP server to the communication PC or are already presentthere as part of the software.

Due to the strenuous requirements for performance and system resourcesof the communication PC, the script support is only to be used forspecial diagnosis tasks.

Time synchronisation, FTP server, Telnet

For synchronisation of the system times, all communication PCs willsynchronise their system time regularly via a time server running on theBAUDIS.

The FTP server and Telnet access serve for software updating of thecommunication PC and for maintenance.

Diagnosis data arising during operation of the drive system (e.g. errorsor diagnosis information such as e.g. temperature, speed, contouringerror, deviation from rules) are polled by the communication PC on theprocess computer node or drive regulator and converted into an XML-basedprotocol. The communication PC makes the diagnosis data available to thediagnosis computer node in an event-based manner (information broker“event”) or in an enquiry-based manner (information broker “parameter”).

In the managers of the diagnosis computer node, the diagnosis data areretrieved or received in an event-based manner from the communication PCof the drive regulator and are further processed (e.g. storage in thedatabase, converted etc.). If diagnosis data are to be displayed on theuser interface, the manager forwards the diagnosis data to theappropriate components in the Servlet container. There the data areprepared, so that they can be transferred by means of enquiry-basedcommunication (polling) or by means of event-based communication (eventchannel) via the data remote connection to the Java Applets, which areembedded in the user interface.

FIGS. 6 and 7 show web-based user interfaces which graphically preparethe required diagnosis data for the user. Thus the diagnosis systemaccording to the invention becomes an instrument which increases themachine availability and also makes complex appliances with a largenumber of drives manageable. Thus with the user interfaces of the typeshown in FIGS. 7 and 8, the machine control station can be supplied withdata for the current machine status, or the production line can beprovided with statistical data for machine availability and formaintenance cycles. But also the machine manufacturer or the drivesupplier can thus have comfortable access to an appliance with a largenumber of technical-physical processes in order to afford rapid,efficient diagnosis and error correction during servicing. This is madepossible by the user of modern web-based technologies or web-based userinterfaces with their inherent versatility. Advantageously, the webinterface can thus run on any client computer, independently of therespective client operating system. Installation of an user interfacespecific to the diagnosis system on the client computer node is nolonger necessary. The web-based user interfaces are operable by the userin a customary and therefore easier manner due to the wide distributionby the Internet. The user interface can be adapted to the client'swishes at reasonable cost.

LIST OF REFERENCE NUMBERS

axle

electric motor

converter

process computer node

communication computer node

switch cabinet

SPS Control computer node.

While certain preferred embodiments of the present invention have beendisclosed in detail, it is to be understood that various modificationsmay be adopted without departing from the spirit of the invention orscope of the following claims.

Key to the Drawings

-   FIG. 1-   Antriebs . . . —drive system-   Diagnoserechnerknoten—diagnosis computer node-   Leitstand—control station-   Diagnose—diagnosis-   Router od.ISDN/Analog—router or ISDN/analogue-   Ferndiagnose—remote diagnosis-   FIG. 2-   Diagnoserechnerknoten—diagnosis computer node-   Diagnosestationen—diagnosis stations-   FIG. 3-   Prozessrechnerknoten—process computer node-   Kommunikationsrechnerknoten—communication computer node-   Diagnoserechnerknoten—diagnosis computer node-   Konfiguration—configuration-   Bedienung—operation-   Diagnose—diagnosis-   Client-Rechnerknoten—client computer node-   FIG. 4-   Zur Prozess . . . —To the process computer plane-   Aufzeichnugs . . . —record manager-   Anlagenmanager—appliance manager-   Ereignis . . . —event manager-   Benutzer . . . —user manager-   Logging . . . —logging manager-   Anlagenubersicht—appliance monitoring-   Logbuch—logbook-   Aufzeichnung—record-   Visualisierung—visualisation-   Inbetriebnahme . . . —installation+service-   Wartung—maintenance-   Ereignisanzeige—event display-   Menu—menu-   Menuhandler—menu handler-   SOAP-Handler—SOAP handler-   Zyklische Daten—cyclical data-   Event+Heartbeat—event+heartbeat-   Diagnose-Rechner . . . —diagnosis computer node-   Firewall—firewall-   Zu den . . . —to the client computer node-   FIG. 5-   Prozess . . . —process computer node-   Kommunikations . . . —communication computer node-   Proprietares protokoll—proprietary protocol-   Informationsbroker—information broker-   Parameter—parameters-   Fehler U. Events—errors and events-   Bedarfsdaten—demand data-   Zyklische Sollwerte—cyclical setpoint values-   Zeitzynchronisation—time synchronisation-   Telnet-Zugang—Telnet access-   Konfigurations . . . —configuration manager-   Skripte—script-   Logging Server—logging server-   Diagnose-Netz—diagnosis network-   Diagnose-Rechnerknoten—diagnosis computer node-   Steuerungs-Netz—control network-   Steuerung—control-   FIG. 6-   Gesamtubersicht—Total monitoring-   Anlagenubersicht—appliance monitoring-   (reading down the left-hand column)-   Appliance status-   Appliance monitoring-   Logbook-   Diagnosis-   Record-   Visualisation-   Service-   Parameter monitor-   Maintenance-   Regulator administration-   Data records-   Events-   Secure drive-   Firmware update-   System functions-   Settings-   User management-   BAUDIS NET setup-   Documentation-   Log off-   FIG. 7-   Antriebsystem—drive system-   Column on left reads same as for FIG. 6

1. A computer network for the configuration, installation, monitoring,error diagnosis and/or error analysis of plural technical-physicalelectric drive processes, which run under the control, regulation and/ormonitoring by plural process computer nodes (4), which are connected viaat least one shared communication system to at least one diagnosiscomputer node in which one or more configuration, monitoring, diagnosisservice(s) and/or function(s) are implemented, which are allocated tothe processes and/or the process computer nodes (4) and/or to the dataprocessing operations running therein, characterised in that: (a) theshared communication system is realised by an Ethernet or another bus orcommunication system operating asynchronously and/or with a stochasticaccess method; (b) a communication unit or computer node isinterconnected between the Ethernet or other bus or communication systemand at least one of the process computer nodes (4) and connects theprocess computer node (4) to the Ethernet or other bus or communicationsystem; (c) the communication unit or communication computer node (5) isformed for communication with the diagnosis computer node via XMLprotocols and/or as an XML-based interface; and (d) the communicationcomputer node (5) is formed as an additional component for therespective process computer node (4).
 2. A network according to claim 1,characterised in that the communication unit or communication computernode (5) is formed for enquiry-based or event-based communication withthe diagnosis computer node.
 3. A network according to claim 1,characterised in that the communication unit is capable of runningentirely or in part on the hardware of the process computer node and/ordiagnosis computer node.
 4. A network according to claim 1,characterised in that for each data exchange each communication unit isallocated a process computer node (4) and/or a technical-physicalprocess or each communication computer node (5) is allocated at leastone technical-physical process or a process computer node (4).
 5. Acomputer network for the configuration, installation, monitoring, errordiagnosis and/or error analysis of plural technical-physical electricdrive processes, which run under the control, regulation and/ormonitoring by plural process computer nodes (4), which are connected viaat least one shared communication system to at least one diagnosiscomputer node in which one or more configuration, monitoring, diagnosisservice(s) and/or function(s) are implemented, which are allocated tothe processes and/or the process computer nodes (4) and/or to the dataprocessing operations running therein, characterised in that: (a) theshared communication system is realised by an Ethernet or another bus orcommunication system operating asynchronously and/or with a stochasticaccess method; (b) a communication unit or computer node isinterconnected between the Ethernet or other bus or communication systemand at least one of the process computer nodes (4) and connects theprocess computer node (4) to the Ethernet or other bus or communicationsystem; (c) for each data exchange each communication unit is allocateda process computer node (4) and/or a technical-physical process or eachcommunication computer node (5) is allocated at least onetechnical-physical process or a process computer node (4); and (d) atleast one of the communication computer nodes (5) is connected to pluralprocess computer nodes via a serial communication system.
 6. A networkaccording to claim 5, characterised in that the communication unit orcommunication computer node (5) is provided with functionalities for anerror search or diagnosis in a region of at least one of the processcomputer nodes and/or technical physical processes.
 7. A networkaccording to claim 5, characterised in that the diagnosis computer nodeis formed for delivering or supporting web-based user interfaces inparticular via data remote transmission or a long-distance trafficnetwork and is provided with the function components corresponding tothe user interfaces.
 8. A network according to claim 5, characterised bya structure corresponding to a client/server architecture with thediagnosis computer node as server.
 9. A diagnosis computer nodeconnected to a computer network, which utilizes a structurecorresponding to a client/server architecture, for configuration,installation, monitoring, error diagnosis and/or analysis of pluraltechnical-physical electric drive processes, which run under controlregulation and/or monitoring by plural process computer nodes (4), saidcomputer network comprising at least one communication computer node(5), wherein said diagnosis computer node is formed as a server withinterfaces to at least one database, for communication with thecommunication and/or process computer nodes and other client computernodes, wherein interfaces to the other client computer nodes are formedas Servlet containers, which provide transmission of diagnosis dataobtainable from the interfaces for communication with the communicationand/or process computer nodes to the client nodes, and the one or moreinterfaces to the communications and/or process computer nodes orcommunication units are realised on the basis of the Ethernet,comprising: (a) a diagnosis channel, which is formed by: one or moreEthernet interfaces allocated to the communication and/or processcomputer node (4); an event management unit with database access, whichis formed for processing the diagnosis data obtained at the Ethernetinterfaces; and an event monitoring unit applied on the basis of theServlet container, which makes available output data from the eventmanagement unit to one or more Applets on external client computernodes; and (b) an appliance management unit having information data viathe configuration of the technical-physical processes together withassociated process computer nodes (4) and one or more functioncomponents, which are formed to visualise the configuration incombination with the client computer node and/or for keeping ready theinformation data for further data processing operations.
 10. A computernode according to claim 9, characterised in that a web server forgenerating and forwarding data obtained from HTML pages by the Servletcontainer is connected downstream of the Servlet container.
 11. Acomputer node according to claim 9, characterised in that the interfacesare installed for communication with the communication and/or processcomputer node via XML protocols and/or the interfaces for communicationwith the client computer nodes via SOAP (Simple Object ProcessProtocol).
 12. A computer node according to claim 9, characterised by acommunication unit installed by program or software technology in such amanner that thereby one or more of the process computer nodes (4) can beconnected to the Ethernet or other bus communication system.
 13. Acommunication computer node (5) or communication unit as a softwareand/or firmware module, connected to a computer network forconfiguration, installation, monitoring, error diagnosis and/or analysisof plural technical-physical electric drive processes, which run undercontrol, regulation and/or monitoring by plural process computer nodes(4), which are connected via at least one shared communication system toat least one diagnosis computer node in which one or more configuration,monitoring, diagnosis services and/or functions are implemented whichare allocated to the processes and/or the process computer nodes (4)and/or to the data processing operations running therein, said sharedcommunication system being realized by an Ethernet or other bus orcommunication system operating asynchronously and/or with a stochasticaccess method characterised by: the communication computer node orcommunication unit comprising a first interface which is allocated tothe at least one diagnosis computer node and which is programmed forcommunication via protocols of the TCP/IP family, including UDP/IP andby one or more second interfaces allocated to one or more of the processcomputer nodes (4), wherein the first and the one or more secondinterfaces may be coupled together via one or more information brokers,which are each formed by program and/or circuit technology as sub-unitsfor bidirectional enquiry-based and/or event-based data communicationbetween the first and second interface and wherein the second interfaceis formed for connection to a serial communication system.
 14. Acommunication computer node (5) or communication unit according to claim13, characterised in that the first interface is formed forcommunication on the basis of XML protocols.
 15. A communicationcomputer node (5) or communication unit as a software and/or firmwaremodule, connected to a computer network for configuration, installation,monitoring, error diagnosis and/or analysis of plural technical-physicalelectric drive processes, which run under control, regulation and/ormonitoring by plural process computer nodes (4), which are connected viaat least one shared communication system to at least one diagnosiscomputer node in which one or more configuration, monitoring, diagnosisservices and/or functions are implemented which are allocated to theprocesses and/or the process computer nodes (4) and/or to the dataprocessing operations running therein, said shared communication systembeing realized by an Ethernet or other bus or communication systemoperating asynchronously and/or with a stochastic access methodcharacterised by: the communication computer node or communication unitcomprising a first interface which is allocated to the at least onediagnosis computer node and which is programmed for communication viaprotocols of the TCP/IP family, including UDP/IP and by one or moresecond interfaces allocated to one or more of the process computer nodes(4), wherein the first and the one or more second interfaces may becoupled together via one or more information brokers, which are eachformed by program and/or circuit technology as sub-units forbidirectional enquiry-based and/or event-based data communicationbetween the first and second interface and wherein the one or moreinformation brokers comprise one or more function components, which areformed for error search or diagnosis in a region of the process computernodes and/or technical-physical processes.
 16. A communication computernode (5) or communication unit as a software and/or firmware module,connected to a computer network for configuration, installation,monitoring, error diagnosis and/or analysis of plural technical-physicalelectric drive processes, which run under control, regulation and/ormonitoring by plural process computer nodes (4), which are connected viaat least one shared communication system to at least one diagnosiscomputer node in which one or more configuration, monitoring, diagnosisservices and/or functions are implemented which are allocated to theprocesses and/or the process computer nodes (4) and/or to the dataprocessing operations running therein, said shared communication systembeing realized by an Ethernet or other bus or communication systemoperating asynchronously and/or with a stochastic access methodcharacterised by: the communication computer node or communication unitcomprising a first interface which is allocated to the at least onediagnosis computer node and which is programmed for communication viaprotocols of the TCP/IP family, including UDP/IP and by one or moresecond interfaces allocated to one or more of the process computer nodes(4), wherein the first and the one or more second interfaces may becoupled together via one or more information brokers, which are eachformed by program and/or circuit technology as sub-units forbidirectional enquiry-based and/or event-based data communicationbetween the first and second interface and wherein plural informationbrokers are installed with different functionalities and are connectedto a connection manager, which is formed by program or circuittechnology as a sub-unit for carrying out pre-determinable prioritystages, according to which a specified one of the plural informationbrokers may be connected to the second interface(s) and each have acommunication requirement at the process computer node(s) (4).
 17. Acommunication computer node (5) or communication unit as a softwareand/or firmware module, connected to a computer network forconfiguration, installation, monitoring, error diagnosis and/or analysisof plural technical-physical electric drive processes, which run undercontrol, regulation and/or monitoring by plural process computer nodes(4), which are connected via at least one shared communication system toat least one diagnosis computer node in which one or more configuration,monitoring, diagnosis services and/or functions are implemented whichare allocated to the processes and/or the process computer nodes (4)and/or to the data processing operations running therein, said sharedcommunication system being realized by an Ethernet or other bus orcommunication system operating asynchronously and/or with a stochasticaccess method characterised by: the communication computer node orcommunication unit comprising a first interface which is allocated tothe at least one diagnosis computer node and which is programmed forcommunication via protocols of the TCP/IP family, including UDP/IP andby one or more second interfaces allocated to one or more of the processcomputer nodes (4), wherein the first and the one or more secondinterfaces may be coupled together via one or more information brokers,which are each formed by program and/or circuit technology as sub-unitsfor bidirectional enquiry-based and/or event-based data communicationbetween the first and second interface and further comprising a softwareinformation broker for bidirectional transmission of firmware or otherdata or complete data records from the first to the second interface(s).18. A communication computer node (5) or communication unit according toclaim 17, characterised in that an FTP (File Transfer Protocol) serveris interconnected between the software information broker and the firstinterface.
 19. A communication computer node (5) or communication unitaccording to claim 17, characterised by the provision of a non-volatilewrite/read memory, in particular flashcard memory, with which one ormore of the information brokers communicate.
 20. A communicationcomputer node (5) or communication unit according to claim 17,characterised by a parameter information broker for realising aninterface which is XML-based for the reading and/or writing ofparameters in one or more allocated process computer nodes (4).
 21. Acommunication computer node (5) or communication unit according to claim17, characterised by an error/event information broker, which is formedfor communication with an XML-based protocol on the basis of TCP/IP viathe first interface and is provided with a test and trigger member whichcan be so configured from outside that if a predetermined event occurs,in the region of the process computer node(s) (4) and/or of thetechnical-physical process, automatically a corresponding messagetransmission is released to the first interface.
 22. A communicationcomputer node (5) or communication unit according to claim 17,characterised by the installation of an interpreter for the running ofscripts which are formed for access to function elements and/orinformation data in the information broker(s) for the purpose ofcarrying out monitoring and diagnosis functions.
 23. A communicationcomputer node (5) or communication unit according to claim 22,characterised in that the interpreter may be so coupled to an FTP (FileTransfer Protocol) server connected to the first interface that scriptsreceived via the first interface may be executed.
 24. A communicationcomputer node (5) or communication unit according to claim 22characterised by said communication computer node or communication unitbeing formed as an additional structural component for a respectiveprocess computer node (4) and/or structural incorporation with a processcomputer node.
 25. A communication unit according to claim 22,characterised by implementation which is at least in part loadable on tothe hardware of a process and/or diagnosis computer node.